<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<title>SoupContentDecoder</title>
<meta name="generator" content="DocBook XSL Stylesheets V1.76.1">
<link rel="home" href="index.html" title="libsoup Reference Manual">
<link rel="up" href="ch03.html" title="Additional Features">
<link rel="prev" href="SoupSessionFeature.html" title="SoupSessionFeature">
<link rel="next" href="SoupContentSniffer.html" title="SoupContentSniffer">
<meta name="generator" content="GTK-Doc V1.18 (XML mode)">
<link rel="stylesheet" href="style.css" type="text/css">
</head>
<body bgcolor="white" text="black" link="#0000FF" vlink="#840084" alink="#0000FF">
<table class="navigation" id="top" width="100%" summary="Navigation header" cellpadding="2" cellspacing="2">
<tr valign="middle">
<td><a accesskey="p" href="SoupSessionFeature.html"><img src="left.png" width="24" height="24" border="0" alt="Prev"></a></td>
<td><a accesskey="u" href="ch03.html"><img src="up.png" width="24" height="24" border="0" alt="Up"></a></td>
<td><a accesskey="h" href="index.html"><img src="home.png" width="24" height="24" border="0" alt="Home"></a></td>
<th width="100%" align="center">libsoup Reference Manual</th>
<td><a accesskey="n" href="SoupContentSniffer.html"><img src="right.png" width="24" height="24" border="0" alt="Next"></a></td>
</tr>
<tr><td colspan="5" class="shortcuts">
<a href="#SoupContentDecoder.synopsis" class="shortcut">Top</a>
                   | 
                  <a href="#SoupContentDecoder.description" class="shortcut">Description</a>
                   | 
                  <a href="#SoupContentDecoder.object-hierarchy" class="shortcut">Object Hierarchy</a>
                   | 
                  <a href="#SoupContentDecoder.implemented-interfaces" class="shortcut">Implemented Interfaces</a>
</td></tr>
</table>
<div class="refentry">
<a name="SoupContentDecoder"></a><div class="titlepage"></div>
<div class="refnamediv"><table width="100%"><tr>
<td valign="top">
<h2><span class="refentrytitle"><a name="SoupContentDecoder.top_of_page"></a>SoupContentDecoder</span></h2>
<p>SoupContentDecoder — Content-Encoding handler</p>
</td>
<td valign="top" align="right"></td>
</tr></table></div>
<div class="refsynopsisdiv">
<a name="SoupContentDecoder.synopsis"></a><h2>Synopsis</h2>
<pre class="synopsis">
#include &lt;libsoup/soup.h&gt;

                    <a class="link" href="SoupContentDecoder.html#SoupContentDecoder-struct" title="SoupContentDecoder">SoupContentDecoder</a>;
</pre>
</div>
<div class="refsect1">
<a name="SoupContentDecoder.object-hierarchy"></a><h2>Object Hierarchy</h2>
<pre class="synopsis">
  <a href="http://library.gnome.org/devel/gobject/unstable/gobject-The-Base-Object-Type.html#GObject">GObject</a>
   +----SoupContentDecoder
</pre>
</div>
<div class="refsect1">
<a name="SoupContentDecoder.implemented-interfaces"></a><h2>Implemented Interfaces</h2>
<p>
SoupContentDecoder implements
 <a class="link" href="SoupSessionFeature.html" title="SoupSessionFeature">SoupSessionFeature</a>.</p>
</div>
<div class="refsect1">
<a name="SoupContentDecoder.description"></a><h2>Description</h2>
<p>
<a class="link" href="SoupContentDecoder.html" title="SoupContentDecoder"><span class="type">SoupContentDecoder</span></a> handles the "Accept-Encoding" header on
outgoing messages, and the "Content-Encoding" header on incoming
ones. If you add it to a session with <a class="link" href="SoupSession.html#soup-session-add-feature" title="soup_session_add_feature ()"><code class="function">soup_session_add_feature()</code></a> or
<a class="link" href="SoupSession.html#soup-session-add-feature-by-type" title="soup_session_add_feature_by_type ()"><code class="function">soup_session_add_feature_by_type()</code></a>, the session will automatically
use Content-Encoding as appropriate.
</p>
<p>
(Note that currently there is no way to (automatically) use
Content-Encoding when sending a request body, or to pick specific
encoding types to support.)
</p>
<p>
If <a class="link" href="SoupContentDecoder.html" title="SoupContentDecoder"><span class="type">SoupContentDecoder</span></a> successfully decodes the Content-Encoding,
it will set the <a class="link" href="SoupMessage.html#SOUP-MESSAGE-CONTENT-DECODED:CAPS"><code class="literal">SOUP_MESSAGE_CONTENT_DECODED</code></a> flag on the message,
and the message body and the chunks in the <a class="link" href="SoupMessage.html#SoupMessage-got-chunk" title='The "got-chunk" signal'><span class="type">"got_chunk"</span></a>
signals will contain the decoded data; however, the message headers
will be unchanged (and so "Content-Encoding" will still be present,
"Content-Length" will describe the original encoded length, etc).
</p>
<p>
If "Content-Encoding" contains any encoding types that
<a class="link" href="SoupContentDecoder.html" title="SoupContentDecoder"><span class="type">SoupContentDecoder</span></a> doesn't recognize, then none of the encodings
will be decoded (and the <a class="link" href="SoupMessage.html#SOUP-MESSAGE-CONTENT-DECODED:CAPS"><code class="literal">SOUP_MESSAGE_CONTENT_DECODED</code></a> flag will
not be set).
</p>
</div>
<div class="refsect1">
<a name="SoupContentDecoder.details"></a><h2>Details</h2>
<div class="refsect2">
<a name="SoupContentDecoder-struct"></a><h3>SoupContentDecoder</h3>
<pre class="programlisting">typedef struct _SoupContentDecoder SoupContentDecoder;</pre>
<p>
</p>
</div>
</div>
</div>
<div class="footer">
<hr>
          Generated by GTK-Doc V1.18</div>
</body>
</html>